behaviour change after project transfer fron base to another

Hi,

in a module A, i have an Object DXL attribut used to display attribut values from objects of an other module B (links between modules A and B).
This code is from

  • Analysis / Wizard,
  • Tools / Support Tools / Convert Layout Dxl to Attribut Dxl
works fine.

I do an project archive, then restore the project on another PC.
I have all modules, all links, my DXL attribut is the same, but nothing is diplayed !!!!

An idea ?

Pierre
PDU - Thu Dec 02 11:39:31 EST 2010

Re: behaviour change after project transfer fron base to another
SystemAdmin - Thu Dec 02 11:47:37 EST 2010

DOORS Analysis Wizard places the module IDs in the traceability code if you select a specific module or a specific link module to be used. If you then archive a project and restore it to another DOORS DB the module IDs will be different and the traceability DXL code in your DXL attribute will not show anything.

Solution is to recreate the DXL attributes.

Re: behaviour change after project transfer fron base to another
PDU - Thu Dec 02 12:25:04 EST 2010

SystemAdmin - Thu Dec 02 11:47:37 EST 2010
DOORS Analysis Wizard places the module IDs in the traceability code if you select a specific module or a specific link module to be used. If you then archive a project and restore it to another DOORS DB the module IDs will be different and the traceability DXL code in your DXL attribute will not show anything.

Solution is to recreate the DXL attributes.

Ok, i see that :
 

//**********
// DXL generated by DOORS traceability wizard on 10 March 2010.
// Wizard version 2.0, DOORS version 9.1.0.2
pragma runLim, 0
string limitModules[1] = {"49eec8ce7f156cde-00000cd8"}
 
......
    for l in all(o->linkModName) do {
        otherVersion = targetVersion l
        otherMod = module(otherVersion)
        if (null otherMod || isDeleted otherMod) continue
        if (!equal(getItem otherMod, (itemFromID limitModules[depth-1]))) continue
......

 


How can i write DXL attribut, doing the same thing, but portable between databases ?

Pierre